Dec 03 14:01:00.558 INFO testing dire-0.3.1 against master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61 for beta-1.31-5
Dec 03 14:01:00.558 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-2/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 03 14:01:01.077 INFO [stdout] 4e1b42308f813e285db76eb9feba01608d7dcf736f0536114640a90af7297c4d
Dec 03 14:01:01.083 INFO running `"docker" "start" "-a" "4e1b42308f813e285db76eb9feba01608d7dcf736f0536114640a90af7297c4d"`
Dec 03 14:01:02.354 INFO [stderr] usermod: no changes
Dec 03 14:01:02.399 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 03 14:01:02.399 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 03 14:01:02.399 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 14:01:02.399 INFO [stderr] files will be included as a binary target:
Dec 03 14:01:02.399 INFO [stderr] 
Dec 03 14:01:02.399 INFO [stderr] * /source/src/main.rs
Dec 03 14:01:02.399 INFO [stderr] 
Dec 03 14:01:02.399 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 14:01:02.399 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 03 14:01:02.399 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 03 14:01:02.399 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 14:01:02.399 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 14:01:02.399 INFO [stderr] 
Dec 03 14:01:02.399 INFO [stderr] For more information on this warning you can consult
Dec 03 14:01:02.399 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 14:01:02.399 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Dec 03 14:01:02.399 INFO [stderr] please set bin.path in Cargo.toml
Dec 03 14:01:02.410 INFO [stderr]    Compiling dire v0.3.1 (/source)
Dec 03 14:01:03.187 INFO [stderr] warning: use of deprecated item 'std::env::home_dir': This function's behavior is unexpected and probably not what you want. Consider using the home_dir function from https://crates.io/crates/dirs instead.
Dec 03 14:01:03.187 INFO [stderr]   --> src/unix.rs:21:24
Dec 03 14:01:03.187 INFO [stderr]    |
Dec 03 14:01:03.187 INFO [stderr] 21 |             let home = env::home_dir().ok_or(DirsError::HomeMissing)?;
Dec 03 14:01:03.187 INFO [stderr]    |                        ^^^^^^^^^^^^^
Dec 03 14:01:03.187 INFO [stderr]    |
Dec 03 14:01:03.187 INFO [stderr]    = note: #[warn(deprecated)] on by default
Dec 03 14:01:03.187 INFO [stderr] 
Dec 03 14:01:04.571 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.19s
Dec 03 14:01:04.574 INFO [stderr] su: No module specific data is present
Dec 03 14:01:05.467 INFO running `"docker" "inspect" "4e1b42308f813e285db76eb9feba01608d7dcf736f0536114640a90af7297c4d"`
Dec 03 14:01:05.799 INFO running `"docker" "rm" "-f" "4e1b42308f813e285db76eb9feba01608d7dcf736f0536114640a90af7297c4d"`
Dec 03 14:01:06.091 INFO [stdout] 4e1b42308f813e285db76eb9feba01608d7dcf736f0536114640a90af7297c4d
Dec 03 14:01:06.097 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-2/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 03 14:01:06.463 INFO [stdout] af5e1242bf794954cb0158cbf90c3abbbfd3af78fe50f286e7f64e77322c482c
Dec 03 14:01:06.465 INFO running `"docker" "start" "-a" "af5e1242bf794954cb0158cbf90c3abbbfd3af78fe50f286e7f64e77322c482c"`
Dec 03 14:01:07.712 INFO [stderr] usermod: no changes
Dec 03 14:01:07.761 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 03 14:01:07.761 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 03 14:01:07.761 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 14:01:07.761 INFO [stderr] files will be included as a binary target:
Dec 03 14:01:07.761 INFO [stderr] 
Dec 03 14:01:07.761 INFO [stderr] * /source/src/main.rs
Dec 03 14:01:07.761 INFO [stderr] 
Dec 03 14:01:07.761 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 14:01:07.761 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 03 14:01:07.761 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 03 14:01:07.761 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 14:01:07.762 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 14:01:07.762 INFO [stderr] 
Dec 03 14:01:07.762 INFO [stderr] For more information on this warning you can consult
Dec 03 14:01:07.762 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 14:01:07.762 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Dec 03 14:01:07.762 INFO [stderr] please set bin.path in Cargo.toml
Dec 03 14:01:07.775 INFO [stderr]    Compiling dire v0.3.1 (/source)
Dec 03 14:01:08.821 INFO [stderr] warning: use of deprecated item 'std::env::home_dir': This function's behavior is unexpected and probably not what you want. Consider using the home_dir function from https://crates.io/crates/dirs instead.
Dec 03 14:01:08.821 INFO [stderr]   --> src/unix.rs:21:24
Dec 03 14:01:08.821 INFO [stderr]    |
Dec 03 14:01:08.821 INFO [stderr] 21 |             let home = env::home_dir().ok_or(DirsError::HomeMissing)?;
Dec 03 14:01:08.821 INFO [stderr]    |                        ^^^^^^^^^^^^^
Dec 03 14:01:08.823 INFO [stderr]    |
Dec 03 14:01:08.827 INFO [stderr]    = note: #[warn(deprecated)] on by default
Dec 03 14:01:08.827 INFO [stderr] 
Dec 03 14:01:09.789 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.04s
Dec 03 14:01:09.799 INFO [stderr] su: No module specific data is present
Dec 03 14:01:10.411 INFO running `"docker" "inspect" "af5e1242bf794954cb0158cbf90c3abbbfd3af78fe50f286e7f64e77322c482c"`
Dec 03 14:01:10.783 INFO running `"docker" "rm" "-f" "af5e1242bf794954cb0158cbf90c3abbbfd3af78fe50f286e7f64e77322c482c"`
Dec 03 14:01:11.063 INFO [stdout] af5e1242bf794954cb0158cbf90c3abbbfd3af78fe50f286e7f64e77322c482c
Dec 03 14:01:11.065 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-2/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 03 14:01:11.535 INFO [stdout] fb35631e16046fb0df2c65100402bdb448b125fba681ae5e18fb6a1bd4d3b8df
Dec 03 14:01:11.537 INFO running `"docker" "start" "-a" "fb35631e16046fb0df2c65100402bdb448b125fba681ae5e18fb6a1bd4d3b8df"`
Dec 03 14:01:12.681 INFO [stderr] usermod: no changes
Dec 03 14:01:12.743 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 03 14:01:12.743 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 03 14:01:12.743 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 14:01:12.743 INFO [stderr] files will be included as a binary target:
Dec 03 14:01:12.743 INFO [stderr] 
Dec 03 14:01:12.743 INFO [stderr] * /source/src/main.rs
Dec 03 14:01:12.743 INFO [stderr] 
Dec 03 14:01:12.743 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 14:01:12.743 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 03 14:01:12.743 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 03 14:01:12.743 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 14:01:12.743 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 14:01:12.743 INFO [stderr] 
Dec 03 14:01:12.743 INFO [stderr] For more information on this warning you can consult
Dec 03 14:01:12.743 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 14:01:12.743 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Dec 03 14:01:12.743 INFO [stderr] please set bin.path in Cargo.toml
Dec 03 14:01:12.758 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.05s
Dec 03 14:01:12.758 INFO [stderr]      Running /target/debug/deps/dire-3726fb2362aa98c6
Dec 03 14:01:12.767 INFO [stdout] 
Dec 03 14:01:12.767 INFO [stdout] running 0 tests
Dec 03 14:01:12.767 INFO [stdout] 
Dec 03 14:01:12.767 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 14:01:12.767 INFO [stdout] 
Dec 03 14:01:12.767 INFO [stderr]      Running /target/debug/deps/dirs-6cb3e38b30211cd3
Dec 03 14:01:12.779 INFO [stdout] 
Dec 03 14:01:12.779 INFO [stderr]    Doc-tests dire
Dec 03 14:01:12.779 INFO [stdout] running 0 tests
Dec 03 14:01:12.779 INFO [stdout] 
Dec 03 14:01:12.779 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 14:01:12.779 INFO [stdout] 
Dec 03 14:01:13.809 INFO [stdout] 
Dec 03 14:01:13.809 INFO [stdout] running 0 tests
Dec 03 14:01:13.809 INFO [stdout] 
Dec 03 14:01:13.809 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 14:01:13.809 INFO [stdout] 
Dec 03 14:01:13.812 INFO [stderr] su: No module specific data is present
Dec 03 14:01:14.438 INFO running `"docker" "inspect" "fb35631e16046fb0df2c65100402bdb448b125fba681ae5e18fb6a1bd4d3b8df"`
Dec 03 14:01:14.741 INFO running `"docker" "rm" "-f" "fb35631e16046fb0df2c65100402bdb448b125fba681ae5e18fb6a1bd4d3b8df"`
Dec 03 14:01:15.038 INFO [stdout] fb35631e16046fb0df2c65100402bdb448b125fba681ae5e18fb6a1bd4d3b8df
